5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
- Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 2-4: Files and Fields

Alpha Fields


An Alpha field can contain numbers, letters, and special characters, such as #, $, and &. Examples include names, addresses, certain account numbers or serial numbers, and text.

The Alpha fields overlay, shown below, allows you to add Alpha specific attributes to those already defined for fields. The alpha field overlay displays after you complete the entries on the Fields specifications screen if the Field Type you select is ALPHA.

Alpha Fields Overlay

The Alpha Fields overlay contains the following fields:

Length designates the number of character positions, or length, of this field up to 32,767 (32K) characters.

Note: APPX does not support fields (or records) longer than 32K characters. If you map an APPX file to a pre-existing RDBMS table, you may find that the table includes a column larger than 32K; such columns are often referred to as memo columns. APPX offers limited support for memo columns. You can access a memo column by defining (in the APPX data dictionary) an ALPHA X(n) field in the corresponding position.

When you read a record that includes a memo column, APPX will only read the first n characters and will truncate any remaining data. If you read a record with hold and APPX would have to truncate a memo field, the read will fail. Reading a record with hold implies that you may try to update the record and APPX will try to prevent you from losing data through truncation. If you need to delete a record that would include truncated data, use partial-record I/O to avoid truncation. You can also use partial-record I/O to update other fields in the record. In general, you should avoid reading memo columns except in those cases where you actually need the data.

Lowercase OK? indicates whether or not a modifiable item on an interactive screen can be entered in upper- and lowercase letters. If 'no' , the entry is stored and displayed exclusively as uppercase, regardless of how a user enters the information. This entry does not affect statements. A lowercase value established with a statement displays as lowercase, even if this specification prohibits lowercase entries.

Descriptive provides a longer, more easily understood alternative to Field Name, one that is not required to be unique within an application. If blank at all default levels, Field Name is used. Refer to the definition of Descriptive in the Common Domain Specifications section of this manual for more information.

Column Headings designates up to two lines of column heading text. The APPX output process facility uses this text to generate standard column heading images for Start of Page and Start of Range class frames. For cosmetic reasons, the length of headings should not exceed the length of a field itself. Refer to Standard Column Heading Image for additional information.

Translate? Indicates if this domain or field is eligible for language translation.  Currently the following field types may be translated (others will have the field protected)  

Token fields  

Alpha & Format fields that have a validation table  

Work fields that are Token, Alpha, Format, or Text
 
It's currently the designer's responsibility to insure that translatable work fields without a validation table are read only.rovides

The Alpha Fields overlay provides two options which are described in the corresponding sections:

Additional Attributes.

Validation Table

Application Design Manual                                         "Powered by Appx Software"

1018

©2006 By APPX Software, Inc. All Rights Reserved